{"text_format":"1","workbook":"xlsx","n_sheets":5,"sheets":["Instructions","STAGE 1 Screening","STAGE 2 Alt. Selection Sheet 1","STAGE 2 Alt. Selection Sheet 2","list"],"not_rendered":{"charts":0,"images":1,"macros":1,"external_links":0,"defined_names":2,"comments":0,"pivot_tables":0},"unopened":[],"bounds":{"document_bytes":16777216,"sheet_cells":100000,"rows_first":2000,"rows_last":500,"rows_between":2000,"halvings":0,"cell_chars":16384,"cell_head_chars":4096},"cells_cut":0,"cells_raw":0,"read":"whole","date_system":"1900"}

{"sheet":"Instructions","index":0,"n_rows":36,"n_cols":12,"rows_kept":36,"cut":false,"hidden":false,"merged":[[4,1,4,12],[26,1,26,10],[26,11,26,12],[27,1,27,10],[27,11,27,12],[16,1,16,10],[17,1,17,10],[18,0,18,12],[20,1,20,10],[19,1,19,10],[19,11,19,12],[21,0,25,0],[12,11,12,12],[13,1,13,10],[14,1,14,10],[25,1,25,10],[0,0,0,12],[7,1,7,10],[7,11,7,12],[15,1,15,10],[8,0,11,0],[6,0,6,12],[2,0,2,12],[5,0,5,12],[13,11,17,12],[1,0,1,12],[13,0,17,0],[10,1,10,10],[11,1,11,10],[8,11,11,12],[8,1,9,10],[12,1,12,10],[21,1,21,10],[20,11,25,12],[22,1,22,10],[23,1,24,10],[30,1,30,10],[30,11,30,12],[28,0,28,12],[29,1,29,10],[29,11,29,12],[34,1,34,10],[34,11,34,12],[35,1,35,10],[35,11,35,12],[31,1,31,10],[31,11,31,12],[32,1,32,10],[32,11,32,12],[33,1,33,10],[33,11,33,12]]}
["KYTC Intersection Control Evaluation (ICE) Form Instructions"]
[{"$error":"#VALUE!"}]
["Since volumes and other conditions typically change at each intersection along a corridor, complete this form for each intersection.  "]
[null,"Cells shaded beige on the following worksheets are data entry fields."]
["ICE Tool Download ","ICE spreadsheet tools (CAP-X, SSI Tool, SPICE, PPEAG, Design Flags Calculator and LCCET) are available for download on the National Academies website."]
["Some data entry fields include pull-down menus or hover-over features. If a pull-down menu does not include an appropriate option, manually type in the information. If more than five alternative intersection types are considered for Stage 1 or 2, insert additional rows to accommodate these."]
["Stage 1 — Screening Worksheet"]
["Workflow","Input Fields",null,null,null,null,null,null,null,null,null,"Recommended Tools & Resources"]
["Project Information","Retrieve project information and existing roadway data from the Enacted Highway Plan, KYTC's HIVEi website, KYTC's Photolog Viewer, and the KYTC Traffic Counts Map.",null,null,null,null,null,null,null,null,null,"KYTC Highway Plan,\nHIVEi,\nKYTC Photolog,\nKYTC Traffic Counts Map"]
[]
[null,"If additional rows are needed for intersections with more than two routes, insert additional rows into the spreadsheet."]
[null,"If traffic volumes are available for each side of the intersection, document the route’s larger AADT value."]
["Context and Equity","•\tUse this section of the form to capture information about land use, trip types generated, and the intersection's development over time. \n•\tContexts are defined based on development density, land uses, and building setbacks. For more information on context classification see KYTC's Highway Design Guidance Manual (HDM) 703.5. ",null,null,null,null,null,null,null,null,null,"Land Use Plans,\nKYTC Photolog,\nHDM 703.5"]
["Intersection Control Alternative Screening","•\tWhen screening intersections, include all feasible and reasonable intersection control types based on the AADT and other site factors. \n•\tPlease note that the recommended spreadsheet tools are for a very high-level screening. They were developed to require minimal inputs, and to apply to traditional and alternative intersection types. They do not address some details of the intersection. \n•\tDocument concerns in the comments. If another tool is used for the Stage 1 capacity or safety assessment, document it in the comments. \n•\tDo not screen out alternatives prematurely based on forecasted traffic data. When in doubt, advance an alternative to Stage 2 for a more detailed assessment.  ",null,null,null,null,null,null,null,null,null,"CAP-X Tool,\nCAP-X Bike/Ped Tool,\nSSI Score Calculator,\nKYTC ICE Form"]
[null,"Enter v/c and scores from the CAP-X and SSI spreadsheet results. "]
[null,"Enter responses for items e-g based on quantitative and qualitative data:  \ne.) Does the intersection type's potential cost (cost to build and cost to maintain) and impacts generated by the intersection's footprint make it a impractical option? Account for environmental, right-of-way, and utility impacts.  \nf.) Can the intersection control type help address the identified needs?\ng.) Will the intersection control type perform well (e.g., acceptable capacity, safety score, accommodate all users)?"]
[null,"•\tUse information documented on the form by the Project Manager (PM) — based on PDT input — to determine which intersection types will advance to Stage 2. Note: The order of the tools and reported outputs does not indicate a priority of one over another in the evaluation of the alternatives. \n•\tProvide brief justifications for eliminating alternatives. \n•\tIf there is a single viable alternative, it may advance through the design phase without further analysis of other alternatives."]
[null,"Submit the Stage 1 Screening Form, along with attachments listed on the form, to the Location Engineer for review. Place this form in the project's file."]
["Stage 2 — Alternative Selection Worksheet (Sheet 1)"]
["Workflow","Input Fields",null,null,null,null,null,null,null,null,null,"Recommended Tools & Resources"]
["Project Information","Enter project information.  ",null,null,null,null,null,null,null,null,null,"Traffic Analysis Software (HCM Methodology)/ PPEAG"]
["Operational Analysis","For Design Vehicle, use the largest vehicle reasonably anticipated at the intersection."]
[null,"•Software that uses HCM methodologies.  Highway Capacity Software (HCS) or the Planning and Preliminary Engineering Applications Guide (PPEAG) Tool for Intersection Control Evaluation (PPEAG-ICE Tool) may be used. \n•Other tools may be used if agreed to by the PDT. Document these tools on the form. \n•Oversaturated conditions or intersections potentially impacted by a nearby intersection's operations may require microsimulation.  "]
[null,"•\tOn the form, document traffic operation results for each alternative. \n•\tThe form reports overall intersection results, but review results for each leg in the attached results from the analysis tools."]
[]
[null,"The form contains a section for opening- and design-year traffic results. If a traffic forecast is unavailable, the PDT should determine the design year and agree on appropriate growth rates for the area. For some project types (e.g., spot improvements), the PDT may determine a design-year analysis is not needed."]
["Motor Vehicle Safety Performance","To conduct a SPICE Stage 2 analysis, a few additional site-specific values are needed. Default values are provided for these inputs so that a planning-level analysis can be carried out as well. For intersections, the inputs are:\n \n•\tIntersection skew angle\n•\tLighting presence \n•\tNumber of approaches with protected, permissive, and protected/permissive signal phasing \n•\tNumber of approaches with right turn on red \n•\tRed-light camera presence \n•\tPedestrian volume \n•\tNumber of lanes crossed by pedestrians \n•\tNumber of bus stops and number of alcohol sales establishments within 1,000 feet of the intersection\n\nRamp terminals require a few additional inputs. See the SPICE tool for more details.\n\nFrom the Results tab, enter the number of predicted design-year crashes from the SPICE tool for each intersection alternative. Use the Anticipated Impact on Safety Performance column to document qualitative safety benefits.",null,null,null,null,null,null,null,null,null,"SPICE"]
["Context and Equity","If an environmental justice study was completed for the project, summarize findings that should be considered (e.g., populations with disabilities, populations living in poverty, populations under 10 or over 74 years of age, zero car households, demographics). Summarize the area's land use and context.",null,null,null,null,null,null,null,null,null,"KYTC Stage 1 ICE Form/ Environmental Justice Study (if available)."]
["Stage 2 — Alternative Selection Worksheet (Sheet 2)"]
["Workflow","Input Fields",null,null,null,null,null,null,null,null,null,"Recommended Tools & Resources"]
["Pedestrian and Bicyclist Safety Assessment","•\tEnter the approximate level of daily activity. Actual counts are not required.  \n•\tEnter Bike and Ped scores from CAP-X.   \n•\tThe PDT has the option of using the Design Flags Calculator Tool to assess pedestrian and bicyclist safety. The number of red and yellow flags can be entered in the ratings columns.",null,null,null,null,null,null,null,null,null,"CAP-X Multimodal Sheets,\nDesign Flags Tool"]
["Environmental, Utility, Right-of-Way Impacts","Document impacts specific to the intersection control type. If impacts are anticipated to be the same for all intersection control types listed, note that the impacts are the same. ",null,null,null,null,null,null,null,null,null,"Preliminary project plans, environmental document"]
["Public Input","Summarize input from the public and stakeholders.",null,null,null,null,null,null,null,null,null,"Public meeting notes"]
["Intersection Costs","•\tInclude preliminary estimates for each intersection type. Estimates should include the cost to build and the approximate cost of right of way and utilities. The PDT has the option of providing cost comparison ratios for intersection control alternative costs rather than dollar amounts. Attach to this form the supporting documentation used for estimates or comparisons.  \n•\tLife-cycle costs include the cost to build, operate, and maintain an intersection. Other considerations include the cost of delay and the cost of predicted collisions.  \n•\tIn the Life-Cycle Costs column, note potential life-cycle costs for the intersection control type or results from the Life-Cycle Cost Estimation Tool. The tool includes default values for cost of delay and collision costs. Check KYTC's DDSA website (under Resources) for KYTC-preferred crash cost values.  Consult the Modal Programs Branch in the Division of Planning for KYTC for the preferred cost of delay.",null,null,null,null,null,null,null,null,null,"KYTC preliminary cost estimate data,\nLCCET"]
["Other Considerations","Include other pertinent information or considerations (e.g., intersection resiliency) for selecting the intersection control type.  "]
["Intersection Control Selection","•\tDuring the Preliminary Line and Grade (PL& G) meeting the PDT should review Stage 2 ICE results and select an intersection control type. Note: The order of the tools and reported outputs does not indicate a priority of one over another in the evaluation of the alternatives. \n•\tDocument the selection and justification on the form and submit it with the DES for approval.",null,null,null,null,null,null,null,null,null,"KYTC Stage 2 ICE Form"]

{"sheet":"STAGE 1 Screening","index":1,"n_rows":29,"n_cols":10,"rows_kept":29,"cut":false,"hidden":false,"merged":[[21,9,21,12],[19,9,19,12],[20,9,20,12],[15,1,15,5],[15,6,15,7],[15,8,15,12],[16,1,16,5],[17,0,17,12],[16,6,16,7],[16,8,16,12],[27,1,27,12],[28,9,28,12],[28,1,28,5],[26,0,26,12],[22,9,22,12],[23,9,23,12],[25,0,25,12],[12,0,12,12],[1,0,2,12],[0,0,0,12],[10,1,10,12],[3,0,3,12],[7,5,7,6],[7,3,7,4],[7,1,7,2],[7,8,7,12],[8,8,8,12],[8,1,8,2],[8,3,8,4],[9,0,9,12],[14,0,14,12],[11,1,11,7],[11,8,11,12],[4,8,4,10],[4,11,4,12],[4,3,4,4],[4,6,4,7],[6,3,6,4],[6,1,6,2],[5,0,5,12],[6,5,6,6],[6,8,6,12],[13,1,13,3],[13,4,13,6],[13,7,13,12],[8,5,8,6]]}
["KYTC Intersection Control Evaluation Forms"]
["Stage 1: Screening\nComplete the following form and append all supporting documentation. Submit completed forms to the Location Engineer for the project's district.\n"]
[]
["Project Information"]
["District",null,"County",null,null,"Item No.",null,null,"No. of Intersection Legs"]
[]
[null,"Prefix and Number",null,"Functional Classification",null,"Current AADT",null,"No. of Lanes","Existing Multimodal Facilities"]
["Mainline Route"]
["Secondary Route"]
[]
["Project Purpose and Need"]
["Existing Intersection Control"]
["Context and Equity"]
["Context Classification",null,null,null,"Likely Travel Needs"]
[]
["Land Use Northwest Quadrant",null,null,null,null,null,"Land Use Northeast Quadrant"]
["Land Use Southwest Quadrant",null,null,null,null,null,"Land Use Southeast Quadrant"]
["Intersection Control Alternative Screening"]
["Intersection or Interchange Alternative","a.) CAP-X v/c ratio *","b.) CAP-X Pedestrian Accommodation Score","c.) CAP-X Bicycle Accommodation Score","d.) SSI Score **","e.) Impractical to implement (considering cost, potential r/w and environmental impacts)?","f.) Meets the transportation purpose and need?","g.) Addresses the key system performance criteria (safety, all roadway users, operations, etc.)? ","h.) Alternative is selected to advance to Stage 2 for further evaluation.","        Justification:"]
[]
[]
[]
[]
[]
[]
["*Attachments: CAP-X and SSI Files, last 5 years crash data for the existing intersection (if applicable)"]
["**If evaluating interchanges and using the Interchange Configuration Safety Tool, note the Expected KABC crash frequency.\n"]
["Comments:"]
["Prepared By:",null,null,null,null,null,null,"Reviewed By:"]

{"sheet":"STAGE 2 Alt. Selection Sheet 1","index":2,"n_rows":37,"n_cols":11,"rows_kept":37,"cut":false,"hidden":false,"merged":[[0,0,0,10],[1,0,2,10],[3,0,3,10],[4,3,4,4],[4,6,4,7],[27,3,27,8],[15,0,15,2],[9,3,9,6],[9,7,9,10],[20,0,20,2],[21,0,21,2],[10,0,10,2],[11,0,11,2],[12,0,12,2],[13,0,13,2],[14,0,14,2],[17,3,17,6],[17,7,17,10],[18,0,18,2],[19,0,19,2],[5,0,5,2],[5,3,5,10],[8,0,9,2],[16,0,17,2],[26,0,26,10],[22,0,22,2],[23,0,23,2],[24,0,25,1],[24,2,25,10],[6,0,6,10],[7,2,7,3],[7,6,7,10],[7,4,7,5],[29,0,29,2],[30,0,30,2],[31,0,31,2],[32,0,32,2],[28,3,28,8],[28,0,28,2],[29,3,29,8],[30,3,30,8],[31,3,31,8],[32,3,32,8],[35,0,35,10],[36,0,36,10],[37,0,37,10],[33,0,34,1],[33,2,34,10]]}
["KYTC Intersection Control Evaluation Forms"]
["Stage 2: Alternative Selection (Sheet 1)\nComplete the following form and append all supporting documentation. Submit it with the Design Executive Summary (DES) to the KYTC Project Manager.\n"]
[]
["Project Information"]
["District",null,"County",null,null,"Item No."]
["Routes and Milepoints"]
["Operational Analysis"]
["Design Vehicle",null,null,null,"Traffic Software Used"]
["Opening Year"]
[null,null,null,"AM Peak Hour",null,null,null,"PM Peak Hour"]
["Intersection Control Alternative",null,null,"Intersection LOS","Overall V/C","Delay (sec.)","95th percentile queue","Intersection LOS","V/C","Delay (sec.)","95th percentile queue"]
[]
[]
[]
[]
[]
["Design Year"]
[null,null,null,"AM Peak Hour",null,null,null,"PM Peak Hour"]
["Intersection Control Alternative",null,null,"Intersection LOS","V/C","Delay (sec.)","95th percentile queue","Intersection LOS","V/C","Delay (sec.)","95th percentile queue"]
[]
[]
[]
[]
[]
["Additional Comments:"]
[]
["Motor Vehicle Safety Performance"]
["Intersection Control Alternative",null,null,"Anticipated Impact on Safety Performance",null,null,null,null,null,"Predicted Total Crashes","Predicted Fatal & Injury Crashes"]
[]
[]
[]
[]
[]
["Additional Comments on  Safety Analysis:"]
[]
["Context and Equity"]
["Summarize environmental justice or equity concerns in the area. Review context information from the ICE Stage 1 form.\n"]

{"sheet":"STAGE 2 Alt. Selection Sheet 2","index":3,"n_rows":35,"n_cols":9,"rows_kept":35,"cut":false,"hidden":false,"merged":[[28,5,28,7],[23,3,23,4],[24,3,24,4],[25,3,25,4],[27,8,27,10],[28,8,28,10],[23,8,23,10],[24,8,24,10],[25,8,25,10],[26,8,26,10],[23,5,23,7],[24,5,24,7],[25,5,25,7],[26,5,26,7],[27,5,27,7],[0,0,0,10],[1,0,1,10],[2,0,2,10],[11,0,11,10],[7,0,7,2],[8,0,8,2],[9,0,9,2],[10,0,10,2],[3,0,3,2],[3,3,3,4],[3,5,3,7],[3,8,3,9],[13,0,13,2],[14,0,14,2],[12,0,12,10],[5,7,5,10],[5,0,5,2],[6,0,6,2],[6,7,6,10],[8,3,8,6],[9,3,9,6],[10,3,10,6],[5,3,5,6],[9,7,9,10],[10,7,10,10],[14,3,14,10],[8,7,8,10],[33,0,33,2],[33,3,33,10],[34,0,35,10],[4,0,4,10],[7,3,7,6],[7,7,7,10],[6,3,6,6],[27,0,27,2],[28,0,28,2],[31,0,31,10],[32,0,32,2],[32,3,32,10],[13,3,13,10],[15,3,15,10],[26,0,26,2],[15,0,15,2],[19,0,19,10],[20,0,20,10],[29,0,29,10],[30,0,30,10],[16,0,16,2],[17,0,17,2],[18,0,18,10],[16,3,16,10],[17,3,17,10],[21,0,21,10],[22,0,22,10],[24,0,24,2],[25,0,25,2],[26,3,26,4],[27,3,27,4],[28,3,28,4]]}
["KYTC Intersection Control Evaluation Forms"]
["Stage 2: Alternative Selection (Sheet 2)\n"]
["Pedestrian and Bicyclist Safety Assessment"]
["Approximate Pedestrian Activity Level",null,null,null,null,"Approximate Bicycle Activity \nLevel"]
["Below, list the rating level from CAP-X for each alternative:"]
["Intersection Control Alternative",null,null,"Pedestrian Accommodations Rating",null,null,null,"Bicycle Accommodations Rating"]
[]
[]
[]
[]
[]
["Environmental, Utility, Right-of-Way Impacts"]
["Summarize issues related to environmental, utility, or right-of-way (including relocations) impacts specific to each alternative."]
[]
[]
[]
[]
[]
["Public Input"]
["Summarize public input received."]
[]
["Intersection Costs"]
["Provide a preliminary cost estimate for each intersection control alternative. The estimate should include right-of-way, utility, and construction costs associated with the intersection. Include life-cycle costs or a discussion of life-cycle costs. The Life-Cycle Cost Estimation Tool may be used."]
["Intersection Control Alternative",null,null,"Cost ($)",null,"Estimate Includes",null,null,"Life-Cycle Costs"]
[]
[]
[]
[]
[]
["Other Considerations"]
[]
["Intersection Control Selection"]
["Intersection Control Selected",null,null,"Justification"]
[]
["*Attachments: Traffic analysis and safety analysis software files, supporting documentation used for intersection cost estimates. "]

{"sheet":"list","index":4,"n_rows":24,"n_cols":18,"rows_kept":24,"cut":false,"hidden":true,"merged":[]}
[]
["Two-Way Stop-Controlled",null,null,null,"Yes",null,"Excellent",null,1,null,"Rural",null,"Arterial",null,"Two-Way Stop-Controlled",null,null,"Low (50/day)"]
["All-Way Stop-Controlled",null,null,null,"No",null,"Good",null,2,null,"Rural Town",null,"Collector",null,"All-Way Stop-Controlled",null,null,"Med Low (240/day)"]
["Signalized Control",null,null,null,"Not Sure",null,"Fair",null,3,null,"Suburban",null,"Local",null,"Signalized Control",null,null,"Med (700/day)"]
["Mini Roundabout",null,null,null,null,null,"Poor",null,4,null,"Urban",null,null,null,"Mini Roundabout",null,null,"Med High (1500/day)"]
["Roundabout \n(1-lane)",null,null,null,null,null,null,null,5,null,"Urban Core",null,null,null,"Roundabout \n(1-lane)",null,null,"High (3200/day)"]
["Roundabout \n(2-lane)",null,null,null,null,null,null,null,6,null,null,null,null,null,"Roundabout \n(2-lane)"]
["Median U-Turn",null,null,null,null,null,null,null,7,null,null,null,null,null,"Median U-Turn"]
["RCUT (Signalized)",null,null,null,null,null,null,null,8,null,null,null,null,null,"RCUT (Signalized)"]
["RCUT (Unsignalized)",null,null,null,null,null,null,null,9,null,null,null,null,null,"RCUT (Unsignalized)"]
["Jughandle",null,null,null,null,null,null,null,10,null,null,null,null,null,"Jughandle"]
["Displaced Left-Turn",null,null,null,null,null,null,null,11,null,null,null,null,null,"Displaced Left-Turn"]
["Continuous Green Tee",null,null,null,null,null,null,null,12,null,null,null,null,null,"Continuous Green Tee"]
["Quadrant Roadway",null,null,null,null,null,null,null,"Various",null,null,null,null,null,"Quadrant Roadway"]
["Thru-Cut (Signalized)",null,null,null,null,null,null,null,null,null,null,null,null,null,"Thru-Cut (Signalized)"]
["Thru-Cut (Unsignalized)",null,null,null,null,null,null,null,null,null,null,null,null,null,"Thru-Cut (Unsignalized)"]
["Bowtie",null,null,null,null,null,null,null,null,null,null,null,null,null,"Bowtie"]
["Diamond Interchange",null,null,null,null,null,null,null,null,null,null,null,null,null,"Not Applicable"]
["Partial Cloverleaf"]
["SPUI"]
["DDI"]
["Double Roundabout Interchange"]
["Other (Type)"]
["Not Applicable"]